home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group95b.txt
/
000047_icon-group-sender _Sat Jun 17 09:36:13 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-09-18
|
1KB
Received: by cheltenham.cs.arizona.edu; Mon, 19 Jun 1995 09:01:38 MST
Date: Sat, 17 Jun 1995 09:36:13 -0500
From: jeffery@runner.jpl.utsa.edu (Clinton L. Jeffery)
Message-Id: <9506171436.AA04497@runner.utsa.edu>
To: H.Lawson@tees.ac.uk
Cc: icon-group@cs.arizona.edu
In-Reply-To: <1995Jun16.172604.22642@leeds.ac.uk> (H.Lawson@tees.ac.uk)
Subject: Re: Perl v. Icon
Content-Length: 833
Errors-To: icon-group-errors@cs.arizona.edu
> From: H.Lawson@tees.ac.uk (Hamish Lawson)
> Could someone familiar with both Perl and Icon give me a (preferably
> reasoned :) comparison of the text-processing abilities of Perl and Icon
Perl's strong suit (for text processing; it has other strong suits) are
regular-expression-based jobs that manipulate text that is structured fairly
simply. Icon's strength comes out in more complex jobs where the patterns
to be matched are more complex than regular expressions would handle
trivially, and where the computation (in your case, text-processing) calls
for complex data structures and/or algorithms. Of course, Icon does quite
nicely for simple data structures & algorithms, too... :)
The kinds of jobs you described are pretty ideal for Icon; I would
write one in Icon and one in Perl, and see which you prefer.